Nfc enhanced augmented reality information overlays

ABSTRACT

Various embodiments are directed to overlaying relevant product information in augmented reality via the use of near-field communication (NFC) and a product selection system. A user may authenticate into an application or user profile. Information about the user in the user profile may be used to determine which products are relevant to the user. Information related to the relevant products may then be displayed to the user in augmented reality, which improves at least the overall shopping and in-store experience.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.17/966,053, filed Oct. 14, 2022, which is a continuation of U.S. patentapplication Ser. No. 16/423,482 filed on May 28, 2019, which isincorporated herein by reference in its entirety.

BACKGROUND

For customers, shopping online may offer certain advantages overshopping in a store. For example, online customers may be able to readvarious product reviews, read numerous user comments, view specificationsheets, view images or videos of products outside of their packaging,etc. prior to purchasing a product. For in-store customers, however,product-related information, such as reviews, comments, or the like maynot be readily available unless the customers perform online searches ofevery product they wish to purchase, which may be a tedious andtime-consuming task.

SUMMARY

Various embodiments are directed to overlaying relevant productinformation in augmented reality via the use of near-field communication(NFC) and a product selection system. A user may authenticate into anapplication or user profile. Information about the user in the userprofile may be used to determine which products are relevant to theuser. Information related to the relevant products may then be displayedto the user in augmented reality, which improves at least the overallshopping and in-store experience.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A illustrates an example data transmission system in accordancewith one or more embodiments.

FIG. 1B illustrates an example sequence diagram for providingauthenticated access in accordance with one or more embodiments.

FIG. 2 illustrates an example system using a contactless card inaccordance with one or more embodiments.

FIG. 3A illustrates an example contactless card in accordance with oneor more embodiments.

FIG. 3B illustrates an example contact pad of a contactless card inaccordance with one or more embodiments.

FIG. 4 illustrates an example sequence diagram relating to securepassword generation in accordance with one or more embodiments.

FIG. 5 illustrates an example password generation for a password managerapplication in accordance with one or more embodiments.

FIG. 6 illustrates another example of a sequence diagram relating tosecure password generation in accordance with one or more embodiments.

FIG. 7 illustrates another example of password generation for a websitein accordance with one or more embodiments.

FIG. 8 illustrates an example flow diagram in accordance with one ormore embodiments.

DETAILED DESCRIPTION

Various embodiments are generally directed to authenticating a user viaa contactless near-field communication (NFC) smartcard, and based on theNFC authentication, overlaying virtual user-relevant, product-relatedinformation adjacent to one or more products in augmented reality (AR).In examples, the NFC authentication may provide the user a personalizedin-store shopping experience. For instance, a shopping profileassociated with the user may be accessed upon NFC authentication.Information associated with or contained in the shopping profile may beused to present in AR product-related information that is relevant tothe user. Information that may be relevant to the user, for example, mayinclude any product corresponding to the user's general shoppinginterests, shopping patterns, budgetary constraints, affinities towardspecific types of sales, dietary restrictions, or the like.

According to embodiments, prior to or upon entering a store (e.g., agrocery store), the user may tap the user's contactless NFC card to amobile computing device, such as a smartphone, a wearable computer,etc., to authenticate the user into an application and access the user'spersonal shopping profile. As will be further described below, thisprocess may be referred to as “one-tap” authentication. The personalshopping profile may include various information related to the shoppingpreferences of the user, e.g., items previously purchased by the user,grocery lists previously created by the user, user-related diet plans,user-related dietary constraints, etc.

As the user moves within the store, for example, a user computing devicemay detect one or more NFC and/or RFID signals, and via these detectedsignals, the computing device may receive information corresponding tovarious types of products. In examples, the information from thedetected signals may be analyzed so as to present only informationrelevant to the user. For instance, if the user is allergic to peanutbutter, information related to peanut butter products may be filteredout and not displayed. As will be further described below, theproduct-related information may include at least in-store customerreviews, external customer reviews, in-store customer comments, externalcustomer comments, information related to product safety, and so on.

The product information may be presented to the user in virtualinformation bubbles, which may be displayed on the user mobile computingdevice and float in an AR space so that they are persistently in closespatial association with the corresponding products or items in thestore. In embodiments, the virtual information bubbles may be colorcoded based on semantic analysis to give a broad overview of positiveand negative reviews, e.g., red may indicate a negative review, greenmay indicate a positive review. At a distance, color may the onlyfeature of the information bubble visible to the user. As the userapproaches a specific product, one or more headlines of the informationbubble may come into view, and when the user gets even closer to theproduct, the customer may be able to read the entire content of theinformation bubble.

In examples, if the user desires to focus on a specific product andignore the other displayed information bubbles, the user may tap theuser mobile computing device on a product-specific NFC and/or RFIDsensor located on or near the product. In other examples, a bar code ofa specific product may be scanned.

In further examples, review and comments related to a product may bepulled from both in-store reviews from a specific store and web-basedreviews of that product. The AR interface may allow these reviews and/orcomments to be filtered and sorted. Moreover, if a user desires toreview a particular product, the user may tap the user's contactlesscard onto the user mobile computing device to authenticate into anapplication, which may allow the user to quickly enter a comment orreview without having to manually log into the application (which theuser can still do).

The term “information bubble” used herein to describe how the productinformation is graphically displayed in AR may be understood to broadlymean any suitable manner in displaying the product information, e.g.,text-only, bubble-shaped graphic, square-shaped graphic,rectangular-shaped graphic, various fonts, sizes, colors, etc.

In previous solutions, product-related information was not readilyavailable to customers when shopping in brick-and-mortar stores. Asdescribed above, one way a customer could obtain product information inthe store was to look up each and every product online, but that processwas a tedious and overly cumbersome task. Moreover, the in-storeshopping experience was not meaningfully personalized to each customer.The embodiments and examples described herein overcome and areadvantageous over the previous solutions in that product-relatedinformation that is relevant to the user is provided in AR during thein-store shopping experience. In at least that regard, personalized,product-related information may be readily available to the user, whichsignificantly improves the overall shopping experience.

Reference is now made to the drawings, where like reference numerals areused to refer to like elements throughout. In the following description,for the purpose of explanation, numerous specific details are set forthin order to provide a thorough understanding thereof. It may be evident,however, that the novel embodiments can be practiced without thesespecific details. In other instances, well-known structures and devicesare shown in block diagram form to facilitate a description thereof. Theintention is to cover all modification, equivalents, and alternativeswithin the scope of the claims.

FIG. 1A illustrates an example data transmission system according to oneor more embodiments. As further discussed below, system 100 may includecontactless card 105, client device 110, network 115, and server 120.Although FIG. 1A illustrates single instances of the components; system100 may include any number of components.

System 100 may include one or more contactless cards 105, which arefurther explained below with reference to FIG. 3A and FIG. 3B. In someembodiments, contactless card 105 may be in wireless communication,utilizing NFC in an example, with client device 110.

System 100 may include client device 110, which may be a network-enabledcomputer. As referred to herein, a network-enabled computer may include,but is not limited to a computer device, or communications deviceincluding, e.g., a server, a network appliance, a personal computer, aworkstation, a phone, a smartphone, a handheld PC, a personal digitalassistant, a thin client, a fat client, an Internet browser, or otherdevice. Client device 110 also may be a mobile computing device, forexample, an iPhone, iPod, iPad from Apple® or any other suitable devicerunning Apple's iOS® operating system, any device running Microsoft'sWindows® Mobile operating system, any device running Google's Android®operating system, and/or any other suitable mobile computing device,such as a smartphone, a tablet, or like wearable mobile device.

The client device 110 device can include a processor and a memory, andit is understood that the processing circuitry may contain additionalcomponents, including processors, memories, error and parity/CRCcheckers, data encoders, anti-collision algorithms, controllers, commanddecoders, security primitives, and tamper-proofing hardware, asnecessary to perform the functions described herein. The client device110 may further include a display and input devices. The display may beany type of device for presenting visual information such as a computermonitor, a flat panel display, and a mobile device screen, includingliquid crystal displays, light-emitting diode displays, plasma panels,and cathode ray tube displays. The input devices may include any devicefor entering information into the user's device that is available andsupported by the user's device, such as a touch-screen, keyboard, mouse,cursor-control device, touch-screen, microphone, digital camera, videorecorder or camcorder. These devices may be used to enter informationand interact with the software and other devices described herein.

In some examples, client device 110 of system 100 may execute one ormore applications, such as software applications, that enable, forexample, network communications with one or more components of system100 and transmit and/or receive data.

Client device 110 may be in communication with one or more servers 120via one or more networks 115 and may operate as a respective front-endto back-end pair with server 120. Client device 110 may transmit, forexample from a mobile device application executing on client device 110,one or more requests to server 120. The one or more requests may beassociated with retrieving data from server 120. Server 120 may receivethe one or more requests from client device 110. Based on the one ormore requests from client device 110, server 120 may be configured toretrieve the requested data from one or more databases (not shown).Based on receipt of the requested data from the one or more databases,server 120 may be configured to transmit the received data to clientdevice 110, the received data being responsive to one or more requests.

System 100 may include one or more networks 115. In some examples,network 115 may be one or more of a wireless network, a wired network orany combination of wireless network and wired network and may beconfigured to connect client device 110 to server 120. For example,network 115 may include one or more of a fiber optics network, a passiveoptical network, a cable network, an Internet network, a satellitenetwork, a wireless local area network (LAN), a Global System for MobileCommunication, a Personal Communication Service, a Personal AreaNetwork, Wireless Application Protocol, Multimedia Messaging Service,Enhanced Messaging Service, Short Message Service, Time DivisionMultiplexing based systems, Code Division Multiple Access (CDMA) basedsystems, D-AMPS, Wi-Fi, Fixed Wireless Data, IEEE 802.11b, 802.15.1,802.11n and 802.11g, Bluetooth, NFC, Radio Frequency Identification(RFID), Wi-Fi, and/or the like.

In addition, network 115 may include, without limitation, telephonelines, fiber optics, IEEE Ethernet 802.3, a wide area network, awireless personal area network, a LAN, or a global network such as theInternet. In addition, network 115 may support an Internet network, awireless communication network, a cellular network, or the like, or anycombination thereof. Network 115 may further include one network, or anynumber of the exemplary types of networks mentioned above, operating asa stand-alone network or in cooperation with each other. Network 115 mayutilize one or more protocols of one or more network elements to whichthey are communicatively coupled. Network 115 may translate to or fromother protocols to one or more protocols of network devices. Althoughnetwork 115 is depicted as a single network, it should be appreciatedthat according to one or more examples, network 115 may include aplurality of interconnected networks, such as, for example, theInternet, a service provider's network, a cable television network,corporate networks, such as credit card association networks, and homenetworks.

System 100 may include one or more servers 120. In some examples, server120 may include one or more processors, which are coupled to the memory.Server 120 may be configured as a central system, server or platform tocontrol and call various data at different times to execute a pluralityof workflow actions. Server 120 may be configured to connect to the oneor more databases. Server 120 may be connected to at least one clientdevice 110.

FIG. 1B illustrates an example sequence diagram for providingauthenticated access according to one or more embodiments. The diagrammay include contactless card 105 and client device 110, which mayinclude an application 122 and processor 124. FIG. 1B may referencesimilar components as illustrated in FIG. 1A.

At step 102, the application 122 communicates with the contactless card105 (e.g., after being brought near the contactless card 105).Communication between the application 122 and the contactless card 105may involve the contactless card 105 being sufficiently close to a cardreader (not shown) of the client device 110 to enable NFC data transferbetween the application 122 and the contactless card 105.

At step 104, after communication has been established between clientdevice 110 and contactless card 105, the contactless card 105 generatesa message authentication code (MAC) cryptogram. In some examples, thismay occur when the contactless card 105 is read by the application 122.In particular, this may occur upon a read, such as an NFC read, of anear field data exchange (NDEF) tag, which may be created in accordancewith the NFC Data Exchange Format.

For example, a reader, such as application 122, may transmit a message,such as an applet select message, with the applet ID of an NDEFproducing applet. Upon confirmation of the selection, a sequence ofselect file messages followed by read file messages may be transmitted.For example, the sequence may include “Select Capabilities file,” “ReadCapabilities file,” and “Select NDEF file.” At this point, a countervalue maintained by the contactless card 105 may be updated orincremented, which may be followed by “Read NDEF file.” At this point,the message may be generated which may include a header and a sharedsecret. Session keys may then be generated. The MAC cryptogram may becreated from the message, which may include the header and the sharedsecret. The MAC cryptogram may then be concatenated with one or moreblocks of random data, and the MAC cryptogram and a random number (RND)may be encrypted with the session key. Thereafter, the cryptogram andthe header may be concatenated, and encoded as ASCII hex and returned inNDEF message format (responsive to the “Read NDEF file” message).

In some examples, the MAC cryptogram may be transmitted as an NDEF tag,and in other examples, the MAC cryptogram may be included with a uniformresource indicator (e.g., as a formatted string).

In some examples, application 122 may be configured to transmit arequest to contactless card 105, the request comprising an instructionto generate a MAC cryptogram.

At step 106, the contactless card 105 sends the MAC cryptogram to theapplication 122. In some examples, the transmission of the MACcryptogram occurs via NFC. However, the present disclosure is notlimited thereto. In other examples, this communication may occur viaBluetooth, Wi-Fi, or other means of wireless data communication.

At step 108, the application 122 communicates the MAC cryptogram to theprocessor 124. At step 112, the processor 124 verifies the MACcryptogram pursuant to an instruction from the application 122. Forexample, the MAC cryptogram may be verified, as explained below.

In some examples, verifying the MAC cryptogram may be performed by adevice other than client device 110, such as a server 120 in datacommunication with the client device 110 (as shown in FIG. 1A). Forexample, processor 124 may output the MAC cryptogram for transmission toserver 120, which may verify the MAC cryptogram.

In some examples, the MAC cryptogram may function as a digital signaturefor purposes of verification. Other digital signature algorithms, suchas public key asymmetric algorithms, e.g., the Digital SignatureAlgorithm and the RSA algorithm, or zero knowledge protocols, may beused to perform this verification.

It may be understood that in some examples, the contactless card 105 mayinitiate communication after the contactless card is brought near theclient device 110. By way of example, the contactless card 105 may sendthe client device 110 a message, for instance, indicating that thecontactless card has established communication. Thereafter, theapplication 122 of client device 110 may proceed to communicate with thecontactless card at step 102, as described above.

FIG. 2 illustrates an example system 200 using a contactless card.System 200 may include a contactless card 205, one or more clientdevices 210, network 215, servers 220, 225, one or more hardwaresecurity modules 230, and a database 235. Although FIG. 2 illustratessingle instances of the components, system 200 may include any number ofcomponents.

System 200 may include one or more contactless cards 205, which arefurther explained below with respect to FIG. 3A and FIG. 3B. In someexamples, contactless card 205 may be in wireless communication, forexample, NFC communication, with client device 210. For example,contactless card 205 may include one or more chips, such as a radiofrequency identification chip, configured to communicate via NFC orother short-range protocols. In other embodiments, contactless card 205may communicate with client device 210 through other means including,but not limited to, Bluetooth, satellite, Wi-Fi, wired communications,and/or any combination of wireless and wired connections. According tosome embodiments, contactless card 205 may be configured to communicatewith card reader 213 (which may otherwise be referred to herein as NFCreader, NFC card reader, or reader) of client device 210 through NFCwhen the contactless card 205 is within range of card reader 213. Inother examples, communications with contactless card 205 may beaccomplished through a physical interface, e.g., a universal serial businterface or a card swipe interface.

System 200 may include client device 210, which may be a network-enabledcomputer. As referred to herein, a network-enabled computer may include,but is not limited to: e.g., a computer device, or communications deviceincluding, e.g., a server, a network appliance, a personal computer, aworkstation, a mobile device, a phone, a handheld PC, a personal digitalassistant, a thin client, a fat client, an Internet browser, or otherdevice. One or more client devices 210 also may be a mobile device; forexample, a mobile device may include an iPhone, iPod, iPad from Apple®or any other mobile device running Apple's iOS® operating system, anydevice running Microsoft's Windows® Mobile operating system, any devicerunning Google's Android® operating system, and/or any other smartphoneor like wearable mobile device. In some examples, the client device 210may be the same as, or similar to, a client device 110 as described withreference to FIG. 1A or FIG. 1B.

Client device 210 may be in communication with one or more servers 220and 225 via one or more networks 215. Client device 210 may transmit,for example from an application 211 executing on client device 210, oneor more requests to one or more servers 220 and 225. The one or morerequests may be associated with retrieving data from one or more servers220 and 225. Servers 220 and 225 may receive the one or more requestsfrom client device 210. Based on the one or more requests from clientdevice 210, one or more servers 220 and 225 may be configured toretrieve the requested data from one or more databases 235. Based onreceipt of the requested data from the one or more databases 235, one ormore servers 220 and 225 may be configured to transmit the received datato client device 210, the received data being responsive to one or morerequests.

System 200 may include one or more hardware security modules (HSM) 230.For example, one or more HSMs 230 may be configured to perform one ormore cryptographic operations as disclosed herein. In some examples, oneor more HSMs 230 may be configured as special purpose security devicesthat are configured to perform the one or more cryptographic operations.The HSMs 230 may be configured such that keys are never revealed outsidethe HSM 230, and instead, are maintained within the HSM 230. Forexample, one or more HSMs 230 may be configured to perform at least oneof key derivations, decryption, and MAC operations. The one or more HSMs230 may be contained within or may be in data communication with,servers 220 and 225.

System 200 may include one or more networks 215. In some examples,network 215 may be one or more of a wireless network, a wired network orany combination of wireless network and wired network, and may beconfigured to connect client device 210 to servers 220 and/or 225. Forexample, network 215 may include one or more of a fiber optics network,a passive optical network, a cable network, a cellular network, anInternet network, a satellite network, a wireless LAN, a Global Systemfor Mobile Communication, a Personal Communication Service, a PersonalArea Network, Wireless Application Protocol, Multimedia MessagingService, Enhanced Messaging Service, Short Message Service, TimeDivision Multiplexing based systems, Code Division Multiple Access based(CDMA) systems, D-AMPS, Wi-Fi, Fixed Wireless Data, IEEE 802.11b,802.15.1, 802.11n and 802.11g, Bluetooth, NFC, RFID, Wi-Fi, and/or anycombination of networks thereof. As a non-limiting example,communications from contactless card 205 and client device 210 mayinclude NFC communication, the cellular network between client device210 and a carrier, and Internet between the carrier and a back-end.

In addition, network 215 may include, without limitation, telephonelines, fiber optics, IEEE Ethernet 802.3, a wide area network, awireless personal area network, a local area network, or a globalnetwork such as the Internet. In addition, network 215 may support anInternet network, a wireless communication network, a cellular network,or the like, or any combination thereof. Network 215 may further includeone network, or any number of the exemplary types of networks mentionedabove, operating as a stand-alone network or in cooperation with eachother. Network 215 may utilize one or more protocols of one or morenetwork elements to which they are communicatively coupled. Network 215may translate to or from other protocols to one or more protocols ofnetwork devices. Although network 215 is depicted as a single network,it should be appreciated that according to one or more examples, network215 may include a plurality of interconnected networks, such as, forexample, the Internet, a service provider's network, a cable televisionnetwork, corporate networks, such as credit card association networks,and home networks.

In various examples according to the present disclosure, client device210 of system 200 may execute one or more applications 211 and includeone or more processors 212, and one or more card readers 213. Forexample, one or more applications 211, such as software applications,may be configured to enable, for example, network communications withone or more components of system 200 and transmit and/or receive data.It is understood that although only single instances of the componentsof client device 210 are illustrated in FIG. 2 , any number of devices210 may be used. Card reader 213 may be configured to read from and/orcommunicate with contactless card 205. In conjunction with the one ormore applications 211, card reader 213 may communicate with thecontactless card 205. In examples, the card reader 213 may includecircuitry or circuitry components, e.g., NFC reader coil, that generatesa magnetic field to allow communication between the client device 210and the contactless card 205.

The application 211 of any of client device 210 may communicate with thecontactless card 205 using short-range wireless communication (e.g.,NFC). The application 211 may be configured to interface with a cardreader 213 of client device 210 configured to communicate with acontactless card 205. As should be noted, those skilled in the art wouldunderstand that a distance of less than twenty centimeters is consistentwith NFC range.

In some embodiments, the application 211 communicates through anassociated reader (e.g., card reader 213) with the contactless card 205.

In some embodiments, card activation may occur without userauthentication. For example, a contactless card 205 may communicate withthe application 211 through the card reader 213 of the client device 210through NFC. The communication (e.g., a tap of the card proximate thecard reader 213 of the client device 210) allows the application 211 toread the data associated with the card and perform an activation. Insome cases, the tap may activate or launch application 211 and theninitiate one or more actions or communications with an account server225 to activate the card for subsequent use. In some cases, if theapplication 211 is not installed on client device 210, a tap of the cardagainst the card reader 213 may initiate a download of the application211 (e.g., navigation to an application download page). Subsequent toinstallation, a tap of the card may activate or launch the application211, and then initiate (e.g., via the application or other back-endcommunication) activation of the card. After activation, the card may beused in various transactions including commercial transactions.

According to some embodiments, the contactless card 205 may include avirtual payment card. In those embodiments, the application 211 mayretrieve information associated with the contactless card 205 byaccessing a digital wallet implemented on the client device 210, whereinthe digital wallet includes the virtual payment card. In some examples,virtual payment card data may include one or more static or dynamicallygenerated virtual card numbers.

Server 220 may include a web server in communication with database 235.Server 225 may include an account server. In some examples, server 220may be configured to validate one or more credentials from contactlesscard 205 and/or client device 210 by comparison with one or morecredentials in database 235. Server 225 may be configured to authorizeone or more requests, such as payment and transaction, from contactlesscard 205 and/or client device 210.

FIG. 3A illustrates one or more contactless cards 300, which may includea payment card, such as a credit card, debit card, or gift card, issuedby a service provider 305 displayed on the front or back of the card300. In some examples, the contactless card 300 is not related to apayment card and may include, without limitation, an identificationcard. In some examples, the payment card may include a dual interfacecontactless payment card. The contactless card 300 may include asubstrate 310, which may include a single layer or one or more laminatedlayers composed of plastics, metals, and other materials. Exemplarysubstrate materials include polyvinyl chloride, polyvinyl chlorideacetate, acrylonitrile butadiene styrene, polycarbonate, polyesters,anodized titanium, palladium, gold, carbon, paper, and biodegradablematerials. In some examples, the contactless card 300 may have physicalcharacteristics compliant with the ID-1 format of the ISO/IEC 7810standard, and the contactless card may otherwise be compliant with theISO/IEC 14443 standard. However, it is understood that the contactlesscard 300 according to the present disclosure may have differentcharacteristics, and the present disclosure does not require acontactless card to be implemented in a payment card.

The contactless card 300 may also include identification information 315displayed on the front and/or back of the card, and a contact pad 320.The contact pad 320 may be configured to establish contact with anothercommunication device, such as a user device, smart phone, laptop,desktop, or tablet computer. The contactless card 300 may also includeprocessing circuitry, antenna and other components not shown in FIG. 3A.These components may be located behind the contact pad 320 or elsewhereon the substrate 310. The contactless card 300 may also include amagnetic strip or tape, which may be located on the back of the card(not shown in FIG. 3A).

As illustrated in FIG. 3B, the contact pad 320 of FIG. 3A may includeprocessing circuitry 325 for storing and processing information,including a microprocessor 330 and a memory 335. It is understood thatthe processing circuitry 325 may contain additional components,including processors, memories, error and parity/CRC checkers, dataencoders, anti-collision algorithms, controllers, command decoders,security primitives and tamper-proofing hardware, as necessary toperform the functions described herein.

The memory 335 may be a read-only memory, write-once read-multiplememory or read/write memory, e.g., RAM, ROM, and EEPROM, and thecontactless card 300 may include one or more of these memories. Aread-only memory may be factory programmable as read-only or one-timeprogrammable. One-time programmability provides the opportunity to writeonce then read many times. A write once/read-multiple memory may beprogrammed at a point in time after the memory chip has left thefactory. Once the memory is programmed, it may not be rewritten, but itmay be read many times. A read/write memory may be programmed andre-programmed many times after leaving the factory. It may also be readmany times.

The memory 335 may be configured to store one or more applets 340, oneor more counters 345, and a customer identifier 350. The one or moreapplets 340 may include one or more software applications configured toexecute on one or more contactless cards, such as Java Card applet.However, it is understood that applets 340 are not limited to Java Cardapplets, and instead may be any software application operable oncontactless cards or other devices having limited memory. The one ormore counters 345 may include a numeric counter sufficient to store aninteger. The customer identifier 350 may include a unique alphanumericidentifier assigned to a user of the contactless card 300, and theidentifier may distinguish the user of the contactless card from othercontactless card users. In some examples, the customer identifier 350may identify both a customer and an account assigned to that customerand may further identify the contactless card associated with thecustomer's account.

The processor and memory elements of the foregoing exemplary embodimentsare described with reference to the contact pad, but the presentdisclosure is not limited thereto. It is understood that these elementsmay be implemented outside of the pad 320 or entirely separate from itor as further elements in addition to processor 330 and memory 335elements located within the contact pad 320.

In some examples, the contactless card 300 may include one or moreantennas 355. The one or more antennas 355 may be placed within thecontactless card 300 and around the processing circuitry 325 of thecontact pad 320. For example, the one or more antennas 355 may beintegral with the processing circuitry 325 and the one or more antennas355 may be used with an external booster coil. As another example, theone or more antennas 355 may be external to the contact pad 320 and theprocessing circuitry 325.

In an embodiment, the coil of contactless card 300 may act as thesecondary of an air core transformer. The terminal may communicate withthe contactless card 300 by cutting power or amplitude modulation. Thecontactless card 300 may infer the data transmitted from the terminalusing the gaps in the contactless card's power connection, which may befunctionally maintained through one or more capacitors. The contactlesscard 300 may communicate back by switching a load on the contactlesscard's coil or load modulation. Load modulation may be detected in theterminal's coil through interference.

As explained above, the contactless cards 300 may be built on a softwareplatform operable on smart cards or other devices having limited memory,such as JavaCard, and one or more or more applications or applets may besecurely executed. Applets may be added to contactless cards to providea one-time password (OTP) for multifactor authentication (MFA) invarious mobile application-based use cases. Applets may be configured torespond to one or more requests, such as near field data exchangerequests, from a reader, such as a mobile NFC reader, and produce anNDEF message that includes a cryptographically secure OTP encoded as anNDEF text tag.

FIG. 4 illustrates an example one-tap authentication using a contactlesscard according to one or more embodiments. As shown, a mobile computingdevice 402 may be a user or client device (which may also be referred toas a user computing device), such as a smartphone, wearable computer,etc. configured to communicate with a contactless card 404. As describedabove, the mobile computing device 402 may include at least an NFC cardreader configured to establish NFC communication with the contactlesscard 404 via an NFC reader coil. It may be understood that thecontactless card 404 may be similar or identical to the contactless card300 described above.

In examples, a shopping application executing on the mobile computingdevice 402 may display a graphical user interface (GUI) module 406 toperform one-tap authentication, AR display, and in some example, one-tappayment. A notification 408 may instruct the user to tap the contactlesscard 404 to the mobile computing device 402 to authenticate into theshopping application. Moreover, in embodiments, a global positioningsystem (GPS) feature or graphic 410 may display the current location ofthe computing device 402 (e.g., Tysons Corner) and may further displaythe closest store(s) within a predefined area of the current location.

Upon the user tapping the contactless card 404 to the mobile computingdevice 402, the contactless card 404 may generate encrypted data andtransmit the same to the computing device 404. Once received, theone-tap GUI module 406 may transmit at least the encrypted data to anauthentication server, which may decrypt the data and verify the datawith a private key stored in the memory of the server. Theauthentication server may then authenticate the user of the contactlesscard 404 and send the mobile computing device 402 confirmation thereof.Thereafter, the one-tap GUI module 406 may display a profile 412 andvarious other information related to the user.

As illustrated, the user profile 412 may display one or more of thefollowing information: the user's name, the user's dietary restrictions(if any), various meal plans that the user may be on (e.g., budget mealplans, protein-based meal plans), diets that the user may be on (e.g.,no-carb diet, fruit-and-vegetable diet), various user favorites (e.g.,favorite snacks, favorite seasonal fruits, favorite proteins, etc.),previous user purchases (e.g., a list of previously purchased productswithin a predefined time period), a list of frequently purchased items,preferences on product ratings (e.g., whether the user prefers onlythree-star rated products and up), any linkable personal shopper systems(e.g., automated shopping assistance devices), and a link for reviews(e.g., a platform that allows the user to give or provide reviews). Itmay be understood that each of the foregoing user-specific informationcan be interactively selectable by the user (directing the user to aseparate GUI or page) and may allow the user to customize any relatedinformation.

In further examples, while shopping or perusing in a store, one-tapauthentication may allow a user to quickly and efficiently open theshopping application with a single tap of the contactless card 404 andenter review(s) of a product. In addition to one-tap authentication, insome examples, a user may be able to perform one-tap payment of certainproducts.

For example, when the contactless card 404 is tapped to the mobilecomputing device 402, a merchant ID and a transaction ID may be sent tothe authentication server. A virtual account number (VAN) generator maybe used to generate virtual card data (e.g., a virtual card number,expiration date, and/or CVV) associated with the contactless card 404.The VAN generator may then transmit the virtual card data, the merchantID, transaction ID, and any usernames and/or addresses corresponding tothe user to one or more merchant servers (for example, the merchantserver(s) may be associated with the store that the user is currentlyshopping in). The merchant server may then process the transaction usingthe data received from the VAN generator, e.g., by generating atransaction record in a transaction database using at least the receivedvirtual card number, expiration date, CVV, etc. The transaction recordmay further include the user's name, billing address, shipping address,and an indication of each item and/or service purchased. The merchantserver may then transmit an order confirmation to the mobile computingdevice 404. Thus, for example, if the user picks out various items topurchase, but wishes to purchase the items with one-tap payment (asopposed to paying for the items in a check-out line), the user may tapthe contactless card 404, arrange delivery of the items (either in-storeor via the shopping application), and walk out of the store.

FIG. 5 illustrates example NFC and RFID signals according to one or moreembodiments. By way of example, various products may be stocked anddisplayed along each side of a grocery store aisle. As shown, on oneside of aisle 502, various soups may be stocked and displayed, e.g.,soup 504, 506, 508, 510. On the other side of the aisle 502, variouspasta-related items may be stocked and displayed, e.g., pasta 534, 536,pasta sauce 538, 540. Information related to these products may betransmitted via signals emitted from one or more NFC and/or RFID tags orsensors.

In examples, the tags or sensors may be located on the productsthemselves or may be arranged near or adjacent to the products, or both.As illustrated, an RFID tag 512 may be arranged on soup 504. Optionally,an NFC tag 513 may be arranged on the soup 504, as indicated by thedashed outline. As will be further described below, one or moresignal(s) 514 from the RFID tag 512 (or the NFC tag 513) may be detectedby an RFID (or NFC) reader of a user computing device 550, such as auser mobile computing device (e.g., smartphone, wearable computer,tablet, etc.). In some examples, one or more RFID or NFC tags may beplaced or arranged next to the soup 504, such as RFID tag 516 and NFCtag 517, which may provide information not only on soup 504, but also onsoup 506 (or any other products that may be stocked and displayednearby).

To increase the signal strength from the tags, a signal amplifier, suchas amplifier 518, may be arranged adjacent to or coupled with any of theRFID tags 512, 516 and/or NFC tags 513, 517. By increasing the signalstrength, the one or more NFC or RFID signals from the sensors 512, 513,516, 517 may be detected by a computing device further away, forexample, at the other end of the aisle 502.

As further shown, an NFC tag 520 may be arranged on soup 506, andoptionally, an RFID tag 521 may also be arranged thereon. Similar to thearrangement of RFID tag 516, NFC tag 517, and signal amplifier 518, anRFID tag 522, NFC tag 523, and signal simplifier 524 may also bearranged adjacent to soup 506. Signal(s) from the RFID tag 522 and NFCtag 523 may include information about not only soup 506, but also aboutsoup 508 (and other adjacent products).

Soup 508 may be different from soup 504 and 506 in that it may have bothan NFC tag 526 and an RFID tag 527 arranged thereon, as indicated by thesolid lines. Whereas, for soup 510, NFC tag 531 and RFID tag 532 mayboth be optional, as shown by the dashed lines. Moreover, signals fromRFID tag 528 and NFC 529 may include information about soups 508 and 510(or any other nearby products) and amplified by signal amplifier 530.

According to embodiments, one or more NFC tags, RFID tags, and/or signalamplifiers may be configured on pasta side of the aisle 502 similarly tothe soup side of the aisle. As shown, pastas 534, 536 and sauces 538,540 may be stocked and displayed on the pasta side. In at least thatregard, signals from the NFC tags and/or RFID tags arranged on the pastaproducts may transmit product-related information, which may be detectedby the user computing device 550.

While FIG. 5 illustrates NFC and/or RFID tags arranged on both theproducts and adjacent to the products, it may be understood that anysuitable arrangment the tags is possible, e.g., tags may be arrangedonly on the products, tags may be arranged only adjancent to theproducts, as long as the product-related information can be sent to theuser computing device 550. Moreover, it may be understood that thesignal amplifiers may be configured in any suitable way to enhance thereach and coverage of the signals from the NFC and/or RFID tags.

FIG. 6 illustrates an example filtration process 600 of product-relatedinformation based on a user profile according to one or moreembodiments. For ease of explanation, at least the products (e.g., soup,pasta, sauce) on each side of aisle 502 illustrated in FIG. 5 will beused in FIG. 6 to describe the filtration process 600.

As a user moves through or walks down the aisle 502, a user computingdevice 602, which belongs to the user, may detect numerous signals fromthe NFC and/or RFID tags arranged on and/or adjacent to the products. Inexamples, an NFC reader configured in the user computing device 602 maydetect all of the NFC signals from the NFC tags. In further examples, anRFID reader configured in the user computing device 602 may detect allof the RFID signals from the RFID tags. The RFID reader, for instance,may be a passive ultra-high frequency (UHF) RFID reader.

Upon receiving the product-related information via the detected signals,the user computing device 602 may filter out any information that may beirrelevant to the user. For example, the user shopping profile mayindicate specific ingredients that the user may be allergic to (or fallunder a dietary restriction). If soups 504, 506, and 508 contain thoseingredients, then product-related information associated with the soups504, 506, and 508 are not displayed in AR, as indicated by the crossouts. In another example, the user shopping profile may indicate thatthe user is on a budget plan and prefers not to spend more than apredetermined amount on specific items. If soups 504, 506, and 508exceed the specified amount, then the product-related informationcorresponding to soups 504, 506, and 508 are not displayed in AR.Relevancy may be understood to refer to, or may be determined based on,how closely the products (or related information) match the variousdescriptions, indications, preferences, etc. specified in the usershopping profile. In examples, a degree of match may be determined,e.g., threshold matching—a predetermined or predefined level ofsimilarly may be considered a match.

As illustrated, if a product is determined not to be irrelevant, such assoup 510, the user computing device 602 may display in AR theinformation associated with that product, such as information bubble604. As will be further described below, information bubble 604 mayinclude an in-store customer comment regarding the soup 510, e.g.,“pairs well with a grilled cheese sandwich,” “wait till the end of monthfor a deal, three for three dollars,” “tasty,” may include a star-basedreview, e.g., “four out of five stars,” etc.

In some instances, one or more criteria may have to be met for theproduct-related information to be displayed. For example, the one ormore criteria may include previously purchased products, productsrelated to a meal plan set by the user, products comporting with adietary restriction of the user, products allowed under a diet that theuser may be on, products related to the user's favorite snacks, productsrelated to the user's favorite seasonal fruits, products related to theuser's favorite protein, discounted products or various specials on theproducts (which may be specified by the user), frequently purchasedproducts by the user, products recommended by a personal shopper orshopping system associated with the user, products that meet a thresholdproduct rating set by the user, etc. For example, soup 510 may be aproduct that comports with the user's dietary restriction and has afive-star product rating, which meets the user-set threshold rating offour stars.

As further shown, the similar filtration process may be applied on thepasta side of the aisle 502. For example, information related to pasta536 and sauce 540 may be excluded (as indicated by the cross outs) fromAR display because they may include ingredients that fall under dietaryrestriction(s), or in other examples, because they fall under athreshold product rating previously set by the user for pasta products.It may be determined that pasta 534 and sauce 538 are not irrelevant,and thus, information bubbles 606 and 608 associated therewith,respectively, may be displayed in AR. Similar to information bubble 604,information bubbles 606 and 608 may include in-store customer commentsand/or customer reviews. For example, information 608 may include acomment that states, “pairs well with angel hair.”

Moreover, information bubbles may be considered relevant when at leastthe information contained therein is related to or based on a history ora pattern of purchases or financial transactions that are unique to theuser and made by the user via the contactless card. For example, if theuser purchases Greek yogurt every time, then yogurt products may berelevant to the user. In another example, if it is determined that theuser prefers to purchase discounted or store-brand products based on theuser's financial transactions, then discounted or store-brand productsmay be more relevant than other brands. In further examples, the usermay selectively view comments and/or reviews of a product by scanning abarcode of that product.

FIG. 7 illustrates example information bubbles displayed in AR space 700according to one or more embodiments. As described above, an informationbubble may include one or more types of information related to aproduct, such as a product identification number (e.g., a unique,searchable number), in-store customer reviews, in-store customercomments, in-store customer ratings, external customer reviews, externalcomments, and other types of external information. In examples, theexternal information may be web-based information, which may include webreviews, product specification sheets, web ratings, visual renderings orimages of various items or components within the products such that theitems or components are viewable in AR outside of the packaging of theproducts, etc. In some examples, the user computing device may retrieveor search for the external information upon obtaining the name of theproduct, product identification number, or any other information relatedto the product that can be searched on the Internet.

As shown in FIG. 7 , four different information bubbles 702, 704, 706,and 708 may be displayed in AR via a user computing device (not shown).It may be understood that FIG. 7 is what the user may see on the displayscreen of the user computing device. The information bubbles may provideinformation one or more of the various products stocked on the “chipsand snack” side of aisle 702, which may include chips 710, 712, 714,722, dip 716, popcorn 718, cracker 720, and so on.

In examples, information bubble 702 may be displayed adjacent to chips710, which may be an externally-retrieved comment and recites “Recalledfor open bags.” According to embodiments, comments, reviews, orinformation that are negative may be color-coded, e.g., in red. Thus,some or all portions of the information bubble 702 may be red toindicate that the information contained in the bubble is negative.

Comments, reviews, or information that are positive may also becolor-coded, e.g., in green. For example, information bubble 704 may bepositioned in AR adjacent to dip 716 and may be an in-store comment orreview (provided by the store or an in-store customer), which states“Marked down $.” Thus, some or all portions of the information bubble704 may be green to indicate positive information. It may be understoodthat what might be negative or positive may be relative and/or specificto the user, e.g., it may be possible that what is positive for one usermay be negative for a different user.

As further shown in FIG. 7 , information bubble 706 may be positionedadjacent to popcorn 718, which is an in-store customer comment or reviewreciting “can do better.” In examples, if there are multiple comments ofthe same product, e.g., popcorn 718, the user computing device may rankeach of the comments based on the user's specific preferences. Ifpopcorn is a product that the user always purchases, then a comment thatincludes an alternative suggestion would be highly ranked, for instance,a comment that may recite, “The other popular popcorn brand is better.”Since the information contained in bubble 706 is negative, again, someor all portions of the bubble may be color-coded in red.

Moreover, information bubble 708 may be displayed or positioned in ARadjacent to cracker 720 and may be an external web review indicatingthat the ranch flavor is the best flavor. Similar to bubble 704,information bubble 708 may be color-coded in green since it containspositive information.

FIG. 8 illustrates an example flow diagram 800 according to one or moreembodiments. It may be understood that the features associated with theillustrated blocks may be performed or executed by one or more computingdevices, e.g., a mobile computing device, and/or processing circuitrycontained therein. Moreover, it may be understood that the blocks inflow diagram 800 are not limited to any specific order, and the one ormore blocks may be performed or executed simultaneously.

At block 802, a user may be authenticated into a shopping applicationvia a contactless card, e.g., tapping the contactless card to the user'smobile computing device. Upon authentication, the mobile computingdevice may retrieve, access, and/or load a personal profile of the user.As described above, the personal profile may indicate various types ofinformation about the user and the user's preferences, e.g., dietaryrestrictions, preferred meal plans, diets, favorites, previouspurchases, frequent purchases, product rating preferences, personalshopper settings, reviews given, etc. Moreover, financial transactiondata and transaction histories associated with the contactless card maybe provided as part of the user's profile.

At block 804, the mobile computing device may determine whether one ormore RFID and/or NFC signals are detected. If detected, productinformation from the detected RFID and/or NFC signals is received. Asset forth above, RFID and/or NFC tags may be arranged on the productsthemselves and/or near the products. Signal amplifiers may be arrangedalong an aisle so as to amplify the signals from the RFID and/or NFCtags.

At block 806, it is determined whether any in-store customer commentsand/or reviews corresponding to the detected products exist. Thein-store customer comments may be provided by the customers shopping inthat store and may be related to the product in any manner, e.g.,product discounts, whether the product tastes good, what the productpairs well with when cooking, etc. It may be understood that externalreviews, such as online reviews by online customers, related to thedetected products may also be obtained.

At block 808, the mobile computing device may determine which of thein-store comments and/or reviews (or external reviews) are relevant tothe user based on the user's profile. If the comments and/or reviews arenot relevant to the user in any way, they are filtered out and notdisplayed to the user. In some examples, relevancy may be determinedbased on a relevancy score (e.g., percentage score). For instance, ifcomments and/or reviews mention a certain relevant product, but is notactually about that product, those comments and/or reviews may still bedisplayed even though they are not directly on point. Advantageously,the user's financial transaction data and history associated with thecontactless card may also be used to determine relevancy. By way ofexample, if it is known that the user always purchases a dozen eggs onevery shopping visit, then eggs will always be considered a relevantproduct.

At block 810, the profile-relevant comments and/or reviews may bedisplayed in AR to the user as information bubbles, which may bearranged adjacent to the relevant product or in close approximateassociation with the product. For example, even if the user moves aroundthe object, the information bubble may appear to be stationary from theperspective of the user. Moreover, as described above, the user canselectively choose which products to focus on, for example, by scanningthe product's barcode.

The components and features of the devices described above may beimplemented using any combination of discrete circuitry, applicationspecific integrated circuits (ASICs), logic gates and/or single chiparchitectures. Further, the features of the devices may be implementedusing microcontrollers, programmable logic arrays and/or microprocessorsor any combination of the foregoing where suitably appropriate. It isnoted that hardware, firmware and/or software elements may becollectively or individually referred to herein as “logic” or “circuit.”

At least one computer-readable storage medium may include instructionsthat, when executed, cause a system to perform any of thecomputer-implemented methods described herein.

Some embodiments may be described using the expression “one embodiment”or “an embodiment” along with their derivatives. These terms mean that aparticular feature, structure, or characteristic described in connectionwith the embodiment is included in at least one embodiment. Theappearances of the phrase “in one embodiment” in various places in thespecification are not necessarily all referring to the same embodiment.Moreover, unless otherwise noted the features described above arerecognized to be used together in any combination. Thus, any featuresdiscussed separately may be employed in combination with each otherunless it is noted that the features are incompatible with each other.

With general reference to notations and nomenclature used herein, thedetailed descriptions herein may be presented in terms of programprocedures executed on a computer or network of computers. Theseprocedural descriptions and representations are used by those skilled inthe art to most effectively convey the substance of their work to othersskilled in the art.

A procedure is here, and generally, conceived to be a self-consistentsequence of operations leading to a desired result. These operations arethose requiring physical manipulations of physical quantities. Usually,though not necessarily, these quantities take the form of electrical,magnetic or optical signals capable of being stored, transferred,combined, compared, and otherwise manipulated. It proves convenient attimes, principally for reasons of common usage, to refer to thesesignals as bits, values, elements, symbols, characters, terms, numbers,or the like. It should be noted, however, that all of these and similarterms are to be associated with the appropriate physical quantities andare merely convenient labels applied to those quantities.

Further, the manipulations performed are often referred to in terms,such as adding or comparing, which are commonly associated with mentaloperations performed by a human operator. No such capability of a humanoperator is necessary, or desirable in most cases, in any of theoperations described herein, which form part of one or more embodiments.Rather, the operations are machine operations.

Some embodiments may be described using the expression “coupled” and“connected” along with their derivatives. These terms are notnecessarily intended as synonyms for each other. For example, someembodiments may be described using the terms “connected” and/or“coupled” to indicate that two or more elements are in direct physicalor electrical contact with each other. The term “coupled,” however, mayalso mean that two or more elements are not in direct contact with eachother, but yet still co-operate or interact with each other.

Various embodiments also relate to apparatus or systems for performingthese operations. This apparatus may be specially constructed for therequired purpose and may be selectively activated or reconfigured by acomputer program stored in the computer. The procedures presented hereinare not inherently related to a particular computer or other apparatus.The required structure for a variety of these machines will appear fromthe description given.

It is emphasized that the Abstract of the Disclosure is provided toallow a reader to quickly ascertain the nature of the technicaldisclosure. It is submitted with the understanding that it will not beused to interpret or limit the scope or meaning of the claims. Inaddition, in the foregoing Detailed Description, it can be seen thatvarious features are grouped together in a single embodiment for thepurpose of streamlining the disclosure. This method of disclosure is notto be interpreted as reflecting an intention that the claimedembodiments require more features than are expressly recited in eachclaim. Rather, as the following claims reflect, inventive subject matterlies in less than all features of a single disclosed embodiment. Thus,the following claims are hereby incorporated into the DetailedDescription, with each claim standing on its own as a separateembodiment. In the appended claims, the terms “including” and “in which”are used as the plain-English equivalents of the respective terms“comprising” and “wherein,” respectively. Moreover, the terms “first,”“second,” “third,” and so forth, are used merely as labels, and are notintended to impose numerical requirements on their objects.

What has been described above includes examples of the disclosedarchitecture. It is, of course, not possible to describe everyconceivable combination of components and/or methodologies, but one ofordinary skill in the art may recognize that many further combinationsand permutations are possible. Accordingly, the novel architecture isintended to embrace all such alterations, modifications and variationsthat fall within the spirit and scope of the appended claims.

What is claimed is:
 1. A method comprising: receiving, by a computingdevice, encrypted data from a contactless card; transmitting, by thedevice to an authentication server, the encrypted data; receiving, bythe device from the authentication server, a confirmation specifying theauthentication server decrypted the encrypted data; receiving, by thedevice from one or more one tags in a store, product informationassociated with a plurality of products; launching, by the device basedon the confirmation, an application including an augmented reality (AR)graphical user interface (GUI); determining, by the application, thatthe device has detected the tag associated with a specific product; anddisplaying, by the application in the AR GUI, the product informationassociated with specific product in one or more information bubblesproximate to the specific product.
 2. The method of claim 1, furthercomprising: accessing, by the device based on the confirmation, apersonal profile associated with a user associated with the contactlesscard based at least in part on the confirmation; and determining, by thedevice based at least in part on the personal profile and the productinformation, whether each of the plurality of products are relevant ornot relevant to the user.
 3. The method of claim 2, wherein the productinformation comprises feedback corresponding to the plurality ofproducts.
 4. The method of claim 3, wherein determining whether each ofthe plurality of products are relevant or not relevant to the user isbased on: analyzing past financial transactions made by the user via thecontactless card at the store; determining one or more shopping patternsand one or more budget-related preferences in the analyzed financialtransactions and whether the one or more shopping patterns and the oneor more budget-related preferences relate to any of the plurality ofproducts with the feedback; determining, based on the personal profile,whether there is a predetermined price not to be exceeded; determining,for each of the plurality of products, whether the product exceeds thepredetermined price; and identifying the related feedback asprofile-relevant.
 5. The method of claim 2, wherein the personal profilecomprises: (i) a dietary restriction of the user, (ii) a meal plan setby the user, (iii) a diet that the user is on, (iv) a favorite snack,(v) a favorite seasonal fruit, (vii) a budget plan, (viii) a list ofproducts purchased during a predefined time period, (ix) a favoriteprotein, (x) a preference for a specific discounted product, (xi) a listof frequently purchased products, (xii) a personal shopper system linkedby the user, and (xiii) a product rating preference set by the user. 6.The method of claim 1, further comprising prior to determining that thedevice has detected the tag: receiving, via the device, web-basedinformation corresponding to the plurality of products based at least inpart on the received product information, wherein the web-basedinformation comprises images of items in each of the plurality ofproducts such that the items are viewable outside a packaging of eachproduct; and overlaying, by the application, the web-based informationcomprising the images of the items and the relevant product informationin the AR GUI proximate to the plurality of products.
 7. The method ofclaim 6, wherein the overlaid product information are color coded in afirst color to indicate a first type of information and in a secondcolor different from the first color to indicate a second type ofinformation different from the first type of information.
 8. The methodof claim 1, wherein the product information is received based onrespective product information numbers for each product received fromthe tags, wherein the tags comprise near-field communication (NFC) tagsor radio frequency identification (RFID) tags.
 9. The method of claim 1,wherein the encrypted data comprises a message authentication code (MAC)cryptogram, wherein the confirmation is further based on theauthentication server verifying the MAC cryptogram, wherein theverification is based on the MAC cryptogram as a digital signature. 10.A computing apparatus comprising: a processor; and a memory storinginstructions that, when executed by the processor, cause the processorto: receive encrypted data from a contactless card; transmit, to anauthentication server, the encrypted data; receive, from theauthentication server, a confirmation specifying the authenticationserver decrypted the encrypted data; receive, from one or more one tagsin a store, product information associated with a plurality of products;launch, based on the confirmation, an application including an augmentedreality (AR) graphical user interface (GUI); detect the tag associatedwith a specific product; and display, in the AR GUI, the productinformation associated with specific product in one or more informationbubbles proximate to the specific product.
 11. The computing apparatusof claim 10, wherein the instructions further cause the processor to:access, based on the confirmation, a personal profile associated with auser associated with the contactless card based at least in part on theconfirmation; and determine, based at least in part on the personalprofile and the product information, whether each of the plurality ofproducts are relevant or not relevant to the user.
 12. The computingapparatus of claim 11, wherein the product information comprisesfeedback corresponding to the plurality of products.
 13. The computingapparatus of claim 10, wherein the instructions further cause theprocessor to, prior to determining that the apparatus has detected thetag: receive web-based information corresponding to the plurality ofproducts based at least in part on the received product information,wherein the web-based information comprises images of items in each ofthe plurality of products such that the items are viewable outside apackaging of each product; and overlay the web-based informationcomprising the images of the items and the relevant product informationin the AR GUI proximate to the plurality of products.
 14. The computingapparatus of claim 10, wherein the product information is received basedon respective product information numbers for each product received fromthe tags, wherein the tags comprise near-field communication (NFC) tagsor radio frequency identification (RFID) tags.
 15. The computingapparatus of claim 10, wherein the encrypted data comprises a messageauthentication code (MAC) cryptogram, wherein the confirmation isfurther based on the authentication server verify the MAC cryptogram,wherein the verification is based on the MAC cryptogram as a digitalsignature.
 16. A non-transitory computer-readable storage medium, thecomputer-readable storage medium including instructions that whenexecuted by a processor, cause the processor to: receive encrypted datafrom a contactless card; transmit, to an authentication server, theencrypted data; receive, from the authentication server, a confirmationspecifying the authentication server decrypted the encrypted data;receive, from one or more one tags in a store, product informationassociated with a plurality of products; launch, based on theconfirmation, an application including an augmented reality (AR)graphical user interface (GUI); detect the tag associated with aspecific product; and display, in the AR GUI, the product informationassociated with specific product in one or more information bubblesproximate to the specific product.
 17. The computer-readable storagemedium of claim 16, wherein the instructions further cause the processorto: access, based on the confirmation, a personal profile associatedwith a user associated with the contactless card based at least in parton the confirmation; and determine, based at least in part on thepersonal profile and the product information, whether each of theplurality of products are relevant or not relevant to the user.
 18. Thecomputer-readable storage medium of claim 17, wherein the productinformation comprises feedback corresponding to the plurality ofproducts.
 19. The computer-readable storage medium of claim 16, whereinthe product information is received based on respective productinformation numbers for each product received from the tags, wherein thetags comprise near-field communication (NFC) tags or radio frequencyidentification (RFID) tags.
 20. The computer-readable storage medium ofclaim 16, wherein the encrypted data comprises a message authenticationcode (MAC) cryptogram, wherein the confirmation is further based on theauthentication server verify the MAC cryptogram, wherein theverification is based on the MAC cryptogram as a digital signature.